ATM customer messaging systems and methods

ABSTRACT

Identification information for a first account holder at a financial institution is received. The first account holder is authenticated based on the identification information. A second account holder at the financial institution is identified as being known to the first account holder. Inputs are received from the first account holder to configure a message to be displayed to the second account holder. The message is displayed to the second account holder from the first account holder.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/870,690 filed Jan. 12, 2018; which is a continuation of U.S. patentapplication Ser. No. 15/075,833, filed Mar. 21, 2016, (now U.S. Pat. No.9,984,411), which is a continuation of U.S. patent application Ser. No.14/549,151, filed Nov. 20, 2014 (now U.S. Pat. No. 9,292,840), which isa continuation-in-part of U.S. patent application Ser. No. 14/076,071,filed Nov. 8, 2013, (now U.S. Pat. No. 9,230,413), which is acontinuation of U.S. patent application Ser. No. 13/441,777, filed Apr.6, 2012 (now U.S. Pat. No. 8,602,296), which claims the benefit of U.S.Provisional Application No. 61/473,053, filed Apr. 7, 2011, the entirecontents of each of which is hereby incorporated by reference.

BACKGROUND

Financial institutions provide various ways for customers to accessaccount information and perform transactions, such as transactionmachines, websites, and brick and mortar locations (e.g., retail bankbranches). Transaction machines, such as automated teller machines(ATMs), may be accessed at various geographic locations, such as banklocations, convenience stores or other stores to facilitate the accountholder's interaction with banking systems. Transaction machines accepttransaction cards such as debit, credit, or stored value cards that areoften used by account holders to purchase items or services or to obtainfunds.

SUMMARY

According to an example embodiment, identification information for afirst account holder at a financial institution is received. The firstaccount holder is authenticated based on the identification information.A second account holder at the financial institution is identified asbeing known to the first account holder. Inputs are received from thefirst account holder to configure a message to be displayed to thesecond account holder. The message from the first account holder isdisplayed to the second account holder.

BRIEF DESCRIPTION OF THE DRAWINGS

The details of one or more implementations of the subject matterdescribed in this specification are set forth in the accompanyingdrawings and the description below. Other features, aspects, andadvantages of the subject matter will become apparent from thedescription, the drawings, and the claims.

FIG. 1 is a schematic diagram of a system that includes an ATMconfigured to communicate with a bank computing system, according to anexample embodiment.

FIG. 2 is a schematic diagram of message configuration logic of FIG. 1.

FIG. 3 is a flow diagram of a process for generating a message throughthe ATM, according to an example embodiment.

FIG. 4 is a schematic screen flow diagram of a process for of sendinganother account holder a happy birthday message through an ATM,according to an example embodiment.

FIG. 5 is a schematic screen flow diagram of a process for receiving andviewing the happy birthday message generated in FIG. 4, according to anexample embodiment.

FIG. 6 is a flow diagram of a process for redeeming a gift attached to amessage, according to an example embodiment.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

The systems and methods described provide a mechanism for usingautomated teller machines (ATMs) or other channels to remind a user ofthe date of a particular event, offer to generate a message, generate amessage based upon that particular event, and forward the messageassociated with the particular event to a recipient through the ATM. Insome embodiments, the particular event may be an event that is personalto another account holder, such as the birthday of another accountholder. In such case, an ATM may alert the user about the other accountholder's upcoming birthday and invite the user to send a message to theother account holder through the ATM. The other account holder mayreceive the message concurrently with the event, e.g., during the monthof his or her birthday, for example.

Referring to FIG. 1 a schematic diagram of a system 100 that includes anATM 150 and a bank computing system 105 is shown. A user 140 mayinteract with the bank computing system 105 through the ATM 150. The ATM150 may comprise an ATM computing system that facilitates the operationof the ATM 150 described throughout the disclosure. It is understoodthat all functions and capabilities described regarding the ATM 150 maybe facilitated and/or implemented by one or more ATM computing systemsconnected with the ATM 150. The ATM 150 may be operated by a financialinstitution, which may also operate the bank computing system 105. Thesystem 100 may include a plurality of ATMs 150 and ATM computing systemsas well as a plurality of financial institutions and bank computingsystems 105. According to some embodiments, the system 100 may beaccessed by an account holder who seeks to perform a financialtransaction, obtain account information, access other products/services,and so on.

In an example embodiment, the bank computing system 105 may be providedor controlled by a bank or other financial institution. The users 140 ofthe ATM 150 may be account holders at the financial institutionoperating the ATM 150. The users may access the bank computing system105 through tellers at retail bank branches, through the financialinstitution's website, or through the ATM 150/ATM computing system. InFIG. 1, for example, the user 140 is shown accessing the bank computingsystem 105 through the ATM 150. In practice, the bank computing system105 may include one or more server computing systems, for example,comprising one or more networked computer servers having a processor andnon-transitory machine readable media. The functions, logic, andcapabilities described herein may therefore be implemented as programlogic stored on the machine-readable media and executable by theprocessor to perform the operations described herein.

The bank computing system 105 may include, among other systems, accountmanagement logic 110, network logic 115, event messaging logic 120, adata storage system 130, and an account database 135. In someembodiments, the account management logic 110 may perform various tasksin connection with accounts held by account holders at the financialinstitution, such as account processing (processing of account debitsand credits), authentication, statement generation, account status,funds transfers, and so on. Account management logic 110 may alsomaintain a log of all transactions that occurred in the past and storedata related to the account in a data storage system 130.

Network logic 115 may be used to allow the bank computing system 105 toconnect and communicate with other systems such as the ATM 150. Oneembodiment of the network logic 115 may be configured to communicatewith the ATM 150 over a proprietary encrypted network. Anotherembodiment of the network logic 115 may be configured to communicatewith the ATM 150 over a public encrypted network. The network logic 115may also connect to the Internet to permit account holders access to thebank computing system 105 through an on-line banking area of a websiteof the bank, through a bank-operated application downloaded on a mobiledevice, etc. Communication connections facilitated by the network logic115 may include wireless connections as well as wired connections.Network logic 115 may also comprise other logic that is configured toprovide a connection to other types of devices such as mobile devices(including cell phones, smart phones, mobile tablets), fax machines,server-based computing systems, and so on.

The event messaging logic 120 including message configuration logic 125may be configured to facilitate the generation and/or the delivery ofmessages created by a user 140 through the ATM 150. The event messaginglogic 120 may communicate with the ATM 150 and/or ATM computing systemsoperating the ATM 150 to facilitate the flow of messages. In someembodiments, event messaging logic 120 logic may also communicate withone or more of the data storage system 130, the account database 135,and the account management logic 110. In some embodiments, the eventmessaging logic 120 receives a message from the ATM 150, delivers themessage to the recipient, and facilitates the viewing of the message bythe recipient.

The event messaging logic 120 may identify other account holders thatare known by the user. For example, the event messaging logic 120 mayidentify a joint account holder (e.g., a spouse of the user) as beingsomebody that is known by the user. In addition to joint accountholders, in some embodiments, information about other account holdersknown by the user may also be obtained from the user, from social mediawebsites, or in another manner. The event messaging logic 120 may gatherinformation about the other account holders using a variety ofmechanisms. For example, the event messaging logic 120 may transferinformation from the data storage system 130.

According to an embodiment, the event messaging logic 120 may alsoreceive information entered into the bank computing system 105 at thetime the financial account was opened for the account holder or theother account holders. Such information can include the birthdate of theaccount holders, for example. In another embodiment, the event messaginglogic 120 can be configured to prompt for information regarding apersonal event associated with one or more account holders. The dataentered may include the name of the personal event (e.g., birthday,wedding anniversary, etc.), date information (e.g., Jan. 3, 2014),personal reminders associated with the personal event (e.g., order cakeand balloons), count-down information for the upcoming date, etc. In yetanother embodiment, members within a community (e.g., an onlinecommunity) in which the user 140 belongs may provide information to theevent messaging logic 120 in a secure mechanism separate from anyaccount related logic (i.e, account management logic 110 or accountdatabase 135). In other embodiments, the user 140 may enter the datathrough a variety of platforms, including through a financialinstitution mobile application, a financial institution based website,an ATM 150, provide the information to a teller working at a branch,etc.

In addition to receiving data into the bank computing system 105, theevent messaging logic 120 may also be configured to provide data (e.g.,date information, name information, personal event name and detailinformation, date count-down information, etc.) to the ATM 150. Forexample, the event messaging logic 120 may communicate with the ATMmessaging logic 185 to transfer data from the bank computing system 105.The ATM 150 may retrieve the date information from the bank computingsystem 105 through the event messaging logic 120 and generate a messagefrom one account holder to another account holder regarding the personalevent through the ATM. The generation of the message is discussed infurther detail below. In some embodiments, the event messaging logic 120may cooperate to perform one or more tasks, such as generating amessage. In some embodiments, as discussed throughout, the message mayhave a gift attached thereto. In such an event, the event messaginglogic 120 may be configured to allow a recipient to reject, accept,and/or redeem the gift attached to the message. Additional informationregarding the receipt of the message is discussed in greater detailfurther below.

The data storage system 130 may include an account database 135. Theaccount database 135 can be structured according to various databasetypes, such as, relational, hierarchical, network, flat or objectrelational. The account database 135 may be configured to store accountinformation such as balances and a log of each transaction processed bythe account management logic 110. The account database 135 may beconfigured to store other activity profile information such as accountpreferences the user has specified, background pictures the user hasuploaded, messages communicated using the system 100, and so on.

In other embodiments, the bank computing system 105 may comprise userinterface logic (not shown) configured to generate customized menus andmenu options for a user at an ATM 150. The bank computing system 105 andthe ATM 150 may cooperate to provide a customized user interface at theATM 150. In one example, the user interface logic may comprise programlogic located at the bank computing system 105, at the ATM 150, or atboth the bank computing system 105 and the ATM 150. Thus, the operationsdescribed herein as being performed by the user interface logic may beperformed either at the bank computing system 105, at the ATM 150, or atboth the bank computing system 105 and the ATM 150. The user interfacelogic may communicate with the event messaging logic 120, the ATMmessaging logic 185, and user interface logic 190 (with the ATM 150) todisplay information to the user 140 and/or a recipient of the message onthe recipient's receiving device (e.g., smartphone, tablet, ATM). Theuser interface logic may generate a graphical user interface forpresentation to a user 140 at the ATM 150 via a display 170, wherein theuser holds a financial account with the financial institution operatingthe ATM 150. The user interface logic may receive information and adjustthe menu options on the display 170 according to data provided by theuser interface logic 190. Other configurations are also possible, someof which are described below.

According to one embodiment, the ATM 150 may include a currencydispenser 155, deposit mechanism 160, card reader 165, display 170,authentication logic 175, transaction processing logic 180, ATMmessaging logic 185, and user interface logic 190. Other hardware mayalso be included, such as a keypad or buttons for receiving user inputs.

The currency dispenser 155 may be configured to dispense currency notes(“cash”) to a user 140 of the ATM 150 from the user's financialinstitution accounts. The currency dispenser 155 may be configured todispense currency in various denominations, as specified by the user140. For example, the currency dispenser 155 may dispense cash inmultiples of fives, tens, or twenties. The deposit mechanism 160 may beconfigured to accept deposits of items such as cash and/or checks intothe ATM 150. In some embodiments, the deposit mechanism 160 may beconfigured to accept deposits without an envelope. In other embodiments,the deposit mechanism 160 can accept deposits placed inside an envelope.

The card reader 165 may be configured to obtain information from atransaction card. The transaction card may include a variety of cardssuch as a credit card, debit card, ATM card, stored value card, etc. Inone embodiment, the card reader 165 obtains information from atransaction card by reading the magnetic stripe (“magstripe”) of thetransaction card. While performing the read operation, the card reader165 may be configured to read the account information and the PINassociated with the card and the account.

The display 170 may be configured to display graphics such as messages,menus, instructions, background photos (e.g., advertisements, etc.),logos, and so on. In one embodiment, the display 170 is a touch screendisplay that is capable of detecting user touches to receive user input.The display 170 allows the user 140 to interact with the ATM 150 inorder to process transactions. The transactions may include withdrawingfunds, purchasing one or more goods or services, transferring funds fromone account to another account, paying a bill or mortgage and so on. Thedisplay 170 may be used to display various customized menu optionstransactions to the user 140.

The authentication logic 175 may communicate with the card reader 165and the bank computing system 105 to gather information about the user140 of the ATM 150. According to some embodiments, the authenticationlogic 175 authenticates a user 140 as being a valid account holderassociated with the transaction card and the corresponding account atthe bank or financial institution. The authentication logic 175 mayemploy a variety of methods to authenticate the user 140, includingcross-checking stored data with received data, biometrics, passwordinformation, pin code, etc.

According to one example embodiment, the transaction processing logic180 may facilitate the processing of financial service transactions of auser 140 at the ATM 150. The ATM 150 may engage a variety transactions,including depositing, withdrawing, currency exchanges, balancetransfers, account balance inquiries, purchases, etc. In someembodiments, the transaction processing logic 124 may cooperate with thebank computing system 105 to ensure that transactions are accuratelydebited/credited to the account held by the user 140. The transactionprocessing logic 180 may also communicate with other computing serversconnected to and/or within the ATM computing system to processtransactions.

In some embodiments, the ATM messaging logic 185 may compriseinstructions stored in non-transitory computer readable media andexecutable by a processor to perform for a variety of functionsdisclosed herein. For example, the ATM messaging logic 185 may promptthe user 140 to send a message to a recipient through the ATM 150. Insome embodiments, the recipient may comprise a joint account holder whoshares a financial account with the user 140. In another embodiment, therecipient may comprise a user of an online community to which the user140/account holder belongs. The ATM messaging logic 185 may alsocommunicate with the bank computing system 105 (e.g., the data storagesystem 130) to retrieve facts regarding a particular date or event. TheATM messaging logic 185 may also be configured to communicate with otherparts of the system (e.g., the card reader 165, authentication logic175, user interface logic 190) to implement and execute the functionsdescribed throughout. For example, the ATM messaging logic 185 maycommunicate with the card reader 165, the account management logic 110,and the data storage system 130 to ascertain the data for generating anddelivering messages through the ATM 150. Further details describingfunctions of the ATM messaging logic 185 are discussed below.

In some embodiments, the ATM 150 may also include user interface logic190. The user interface logic 190 generates a graphical user interfacefor presentation to the user 140 at the ATM 150 via the display 170. Theuser interface logic 190 may be configured to generate a graphicalinterface with customized menu options displayable to each user 140. Forexample, a menu option may be provided to the user to select a newbackground image. For example, the user 140 may be permitted to selectfrom a variety of standard background images available at the ATM 150.As another example, the user 140 may be permitted to upload a newbackground image through an on-line banking website provided by the bankcomputing system 105. In one embodiment, the background picture 560 maybe a message that the user 140 or another individual such as a relativehas uploaded (e.g., “Happy birthday, Mom!)”. The menu may be assigned ascore that is determined based on the amount of time (or the number ofvisits to a transaction machine) it has been since the user 140 lastviewed a menu option to select a custom image.

The user interface logic 190 may also generate a graphical interface fordisplaying and creating content for event messages at the ATM 150. Thecontent may include text, graphics, vocals, video, memes, etc. Forexample, the user 140 may be permitted to enter a personalized message,select from an option of standard messages, select a particularbackground color scheme or theme, or upload a personal photo for displayto a recipient. In other embodiments, the user 140 may also be permittedto upload a meme, attach a short video or gif, sketch a drawing, etc.The user interface logic 190 may provide a variety of systems, hardware,and/or software to allow a user 140 to capture the content for use withthe event messaging logic 120. For example, interfaces such as keypads,touch pads or screens, video camera, photo camera, microphones, andrelated software may be employed by the user interface logic 190 toallow the ATM 150 to capture content entered by the user 140.

Referring to FIG. 2, the message configuration logic 125 is shown ingreater detail. The message configuration logic 125 includes recipientselection logic 205, trigger configuration logic 210, message typeselection logic 215, and message content logic 220. The messageconfiguration logic 125 may be accessed by the user at an ATM, viaon-line banking, via mobile banking, or in another manner.

The recipient selection logic 205 is configured select a messagerecipient based on user inputs. In one embodiment, the potentialrecipients to whom the user may send message may be limited to jointaccount holders. In such an arrangement, the recipient selection logic205 may identify whether there are any joint account holders associatedwith the user and, if so, select the joint account holder as a potentialmessage recipient. In other embodiments, the user may also be permittedto send message to other recipients (i.e., people that are not jointaccount holders). For example, account holders may opt-in or opt-out ofreceiving messages from other account holders. For account holders thatopt in to such an arrangement, such account holders may also agree tohaving limited personal information about themselves (e.g., name andcity of residence) displayed to other account holders to facilitateestablishing connections between account holders (i.e., account holdersthat know each other). Further steps (e.g., transmission and approval offriend requests) may also be taken to facilitate the establishment ofvalid connections.

In another embodiment, the recipient selection logic 205 may beconfigured to integrate the system 100 with social media websites (e.g.,Facebook, Twitter, Instagram, etc.). For example, the system may providethe option for a user to provide login credentials (login ID andpassword) for a social media website. Using the login credentials, therecipient selection logic 205 may then access the user's account on thesocial media website and obtain a list of the user's friends/connectionson the social media website. This list may then be compared against thesocial media website login credentials of other account holders for whomsuch login credentials have already been obtained to identify potentialconnections. Again, steps (e.g., transmission and approval of furtherfriend requests within the context of the system 100) may also be takento facilitate the establishment of valid connections (to accommodatesituations where an individual has been “friended” on the social mediawebsite, but the user does not wish to establish a connection in thecontext of the system 100). As another example, where a social mediawebsite has various “levels” of friends, the user may designate thefriend levels on the social media website from whom the user is willingto accept messages in the system 100.

The trigger configuration logic 210 is configured to configure a messagetrigger based on user inputs. The message trigger determines, at leastin part, when the message is displayed to the recipient. (The timing isalso dependent on when the recipient accesses a banking channel. Hence,for messages displayed via an ATM, for example, another factor wouldinclude the timing of the user's visit to the ATM.) Various types ofmessage triggers may be used. For example, the message trigger may bedate-based, and the message may be displayed concurrently with when aparticular event occurs. For example, if the message to be sent isdate-driven (e.g., a happy birthday message, a happy anniversarymessage, etc.), the user may indicate the date on which the eventoccurs. For example, for a happy birthday message, the recipient'sbirthday is Jan. 1, 1981, the message may be displayed when both (1) thecurrent date is within two week window following January 1, and (2) therecipient is currently making a visit to an ATM. Whether the event isdeemed “concurrent” may be determined by default or based on userinputs. For example, the window may be selected by default by thetrigger configuration logic 210, e.g., to be a two-week window. In otherembodiments, the window may be selectable in response to inputs receivedfrom the user when the message is configured. For example, based on theuser inputs, a one month window may be selected.

The message trigger may be based on other parameters besides date. Forexample, the message trigger may be based on account balances. Forexample, if the recipient maintains a savings goal in online banking,then the user may be provided with a message that states: “Recipient isworking towards reaching a savings goal. Would you like to sendRecipient a congratulatory message when that goal is reached?” Assumingthe user answers affirmatively, then when the recipient meets thesavings goal, a message may be sent to the recipient from the user thatstates: “Congratulations on meeting your savings goal!”

As another example, the message trigger may be based on transactionactivity, such as the location of one or more transactions performed bythe recipient. For example, the bank computing system 105 may determinewhether the recipient is traveling (e.g., based on usage of a creditcard at a restaurant in a different state than the state in which therecipient lives). In such a case, the user may configure a message thatis configured to be sent to the recipient when it is detected that therecipient is traveling (e.g., “Safe travels!”).

The message trigger may also be based on a setting that dictates that amessage be sent each time the recipient uses an ATM. For example, theuser may generate a plurality of messages (e.g., 5, 10, 20, 50 or more).For example, spouse A may generate a series of messages to be deliveredto spouse B. The system may cycle through the messages each time spouseB uses an ATM, such that spouse B is provided with an uplifting messagefrom spouse A (e.g., “Have a great day, honey!) whenever spouse B usesan ATM.

The message type selection logic 215 is configured to select a messagetype based on user inputs. For example, the message may strictly be amessage with no further added content. As another example, the messagemay be a message in combination with a gift. In such an example, themessage type selection logic 215 may be configured to select a giftbased on user inputs. For example, the gift may be a gift of cash. Forexample, user inputs may be received from the user that indicate a daterange, provide the happy birthday message, and provide a designation ofa dollar amount to be given as a gift (e.g. $40). Then, the next timethe recipient uses an ATM, the recipient the user may be provided withthe happy birthday message, and an extra $40 in cash may be dispensed tothe recipient to complete the gift process.

As another example, the user may have accumulated rewards points at anumber of merchants. The message type selection logic 215 may beconfigured to receive user inputs that designate gift options from whichthe recipient may select. For example, the recipient may be providedwith the option to select $40 worth of rewards points from merchant A,$40 worth of rewards points from merchant B, or $40 worth of rewardspoints from merchant C. The recipient may then select one of theoptions, e.g., and be provided with a gift card from that merchant.

The message content logic 220 is configured to determine message contentbased on user inputs. In one embodiment, the user selects from apredetermined set of message templates. For example, the system mayprovide a series of common/standardized messages from which the user mayselect (e.g., “Happy Birthday,” “Happy Anniversary,” so on). In otherembodiments, the text of the message is received from the recipient.

In some embodiments, the message content logic 220 may also beconfigured to filter message content, i.e., in situations where the useris permitted to generate the text of the message. For example, themessage content logic 220 may detect situations where the messagecontent is deemed inappropriate. In one embodiment, the message contentlogic 220 may provide a default appropriateness threshold thatimplements a minimal level of filtering. This may be a user-selectablesetting, such that any given user can also select a higher level offiltering if desired.

In some embodiments, the message configuration logic 125 is configuredto scan calendar tools for dates (e.g., Google Calendar, MicrosoftOutlook, and so on). For example, the user may be prompted to providelogin credentials for an online calendar program, prompted to identify alocally executing calendar program, etc. The message configuration logic125 may then scan for events that are scheduled to recur on a yearlybasis, on the assumption that a such a recurring event may be abirthday, anniversary, or the like. As another example, the messageconfiguration logic 125 may be configured to scan for keywords in thecalendar entries that are likely to be associated with a personal event.For example, the message configuration logic 125 may be configured toscan for a proper noun (i.e., a person's name) coupled with a keywordsuch as “birthday” or “b-day.” The message configuration logic 125 mayalso be configured to store information about the message for futureuse. For example, in the context of a wedding anniversary, the messageconfiguration logic may be configured to store information about themessage, such that in subsequent years, the user may be prompted whetherthe user wishes to send the message again in the current year.

Referring to FIG. 3, a flow diagram of a process 300 for generating amessage through the ATM 150 according to an example embodiment is shown.For purposes of providing an example, it is assumed in the discussion ofFIG. 3 that the user is using at an ATM. As will be appreciated,however, the user may also access the features described herein viaanother channel, such as through a financial institution website, anapplication on a mobile device, through in-store banking, etc.

The process 300 may be implemented by one or more portions of the system100 shown FIG. 1, including the bank computing system 105 (e.g., theaccount management logic 110, the event messaging logic 120, the datastorage system 130, and the account database 135) and the ATM 150 (e.g.,the card reader 165, the display 170, the authentication logic 175, thetransaction processing logic 180, the ATM messaging logic 185, and theuser interface logic 190). The process 300 may involve receiving ATM 150authentication information (310). Authentication information maycomprise any information that authenticates the user 140 of the ATM 150as the account holder at the financial institution operating the ATM150. For example, authentication information may comprise a pin numberentered by the user 140 at the ATM 150 upon providing a transaction cardto the card reader 165. Authentication information may also comprisedata read from the transaction card, such as track 1 data and track 2data.

The process 300 may further involve authenticating the user 140 of theATM 150 (320). The authentication information received at step 210 maybe used to authenticate the user 140. In some embodiments, the user 140may be authenticated when the user 140 is physically present at the ATM150. In other embodiments, the user 140 may be authenticated when theuser 140 is within a proximity of the ATM 150 by way of a connectedmobile device (e.g., a smartphone, a tablet, etc.). In one embodiment,the ATM 150 may use information from a transaction card as retrieved bythe card reader 165 to authenticate a user 140. In other embodiments,the ATM 150 may use biometric information to authenticate the user 140of the ATM 150. It is understood that a variety of tools and methods maybe used to authenticate a user 140 of the ATM 150.

After the user authenticates at the ATM 150, the user may be providedwith a variety of menu options (e.g., withdraw cash, make a deposit,purchase stamps, and so on). One of the menu options may be an option toconfigure personal messages to other account holders. The user mayprovide input(s) at the ATM (e.g., depress a button indicating personalmessaging) to obtain access to the personal messaging features. In otherembodiments, e.g., where the user can only send messages to a jointaccount holder, the user may simply be prompted to configure a messageto be sent to the joint account holder if the user has not already doneso.

The process 300 may identify other account holders known to the user(330). For example, the ATM 150 may communicate with the bank computingsystem 105 to identify any joint account holders that may exist. Asanother example, the user may be prompted to provide name/addressinformation, social media login credentials, and/or other informationthat may be used to establish connections and thereby identify otherpeople known by the user, as discussed above.

The process 300 may comprise identifying an upcoming personal event forany identified account holders (340). In some embodiments, the ATMmessaging logic 185 may be configured to communicate with differentlogic modules or systems to obtain identifying information for apersonal event associated with one or more account holders. In someembodiments, the ATM messaging logic 185 may communicate with the eventmessaging logic 120 and/or the data storage system 130 to determine thedata associated with the upcoming personal event (e.g., dateinformation, name of event, count down until the date, etc.). In otherembodiments, the ATM 150 may be structured to generate an invitation tothe user 140, prompting the user 140 to send a message based upon thedata relating to the personal event received from the event messaginglogic 120 and/or data storage system 130.

The process 300 may comprise receiving inputs to configure messages(350) and, based on the inputs, generating the messages associated withthe personal event (360). The ATM messaging logic 185 may be configuredto generate the message for the user 140 to transfer to a recipient(e.g., a joint account holder, another account holder, etc.). Aspreviously indicated, according to some embodiments, the event messagemay be associated with a cyclical event. For example, the event messagemay be related to a birthdate, an adoption date, an anniversary, etc.According to other embodiments, the event messages may be associatedwith a particular one-time celebratory event, such as a graduation day,house warming, new job, stellar report card, etc. In one example,customer names are dynamically populated on the ATM 150 display 170.Using the ATM 150, customers are able to wish each other a happybirthday through the ATM 150.

In one example embodiment, Customer A and Customer B share a jointchecking account at a financial institution. Customer A's birthday is inMarch. In February, Customer B visits the ATM 150 and is asked throughthe ATM 150 computing system if Customer B would like to send CustomerA, the joint account holder, a happy birthday message in March. IfCustomer B opts in and chooses to send the birthday wishes through thehappy birthday message, then Customer A would receive and view thepersonalized birthday message from Customer B. In one embodiment, themessage may wish Customer B a happy birthday month.

The content of the message may include a simple message relating to apersonal event, such as “Happy Birthday!” The message may be a standardmessage populated by the ATM messaging logic 185 or the message may becustomized. The message may also be conveyed in any language understoodby the responder, for example, Spanish, Mandarin, French, English, etc.In one embodiment, the ATM 150 may dynamically populate the jointaccount holder's name on the screen/display 170 and a message may bepopulated based on the joint account holder's name and the event-relateddata retrieved by the ATM messaging logic 185. In another embodiment,the message may include a voice message, vocal recording, musical jingle(e.g., the happy birthday tune/song), a short video, a meme, an animatedgraphical interchange format (gif) content, etc. The user 140 may createor customize the message in a variety of ways. The example the user 140may enter personalized messages. The user 140 may sketch messages and orpictures using a touch screen for example. The user 140 may create andselect a background color, theme, wallpaper, etc. The user 140 may alsomake a selection from preloaded standard messages available through theATM 150. In some embodiments, the user 140 may upload one or more photosfor display in the background of the message.

In some embodiments, the user 140 may be permitted to attach a gift tothe message for the recipient. The gift may comprise a variety of forms,including but not limited to cash, demand deposit account deposit,currency towards student loans, money for a particular trip (e.g.,vacation), a credit card payment, a home payment, rent payment, a carpayment, a transfer of rewards points, etc. The user 140 may bepermitted to designate a restricted gift (e.g., only money towardsstudent loans), designate a gift with limited options selectable by therecipient (e.g., $300 car payment or $300 rent payment), or designate anunrestricted gift in which the recipient may choose the form of thegift. According to some embodiments, the user may have the option toselect the channel(s) through which the recipient receives the messageor the gift. For example, the user may make a selection to provide themessage or gift to the recipient through an ATM 150, a mobileapplication, a website (e.g., a financial institution's website), etc.

The process 300 may include sending the message to the recipient (370).The ATM messaging logic 185 may be configured to send the message to therecipient. In another embodiment, the ATM messaging logic 185 isconfigured to send the message to the event messaging logic 120, whichthen sends the message to the recipient. In yet another embodiment, theuser 140 may designate when the user 140 would like the messagedelivered (e.g, during the month of the date, a particular number ofdays prior to the date, etc.). In another embodiment, the system 100 maybe configured to propose a delivery date to the user 140, and the user140 can accept or deny the proposed delivery date. Again, the messagingservice may integrate multiple platforms during the implementation ofgenerating and sending the messages. Hence, while an ATM is given as anexample in FIG. 3, the recipient may also receive the message through ana financial institution website, an application on a mobile device,through in-store banking, etc.

FIG. 4 is a schematic screen flow diagram of a process for a sender tosend another account holder a happy birthday message through an ATM,according to an example embodiment. Screen 400 prompts a user 140 tosend an ATM 150 birthday card (e.g., a message as described throughout)to a recipient (e.g., the other account holder). In this example, it isassumed that the user has not already provided a menu-based inputindicating an interest in configuring a personal message for anotheraccount holder, but rather is spontaneously prompted to do so by the ATM150. In some embodiments, the computing system of the ATM 150 may beconfigured to dynamically populate the electronic card with the otheraccount holder's name displayed in the recipient name field. The user140 may decline the invitation to send a card by selecting the “No,thank you” field shown in screen 400, which may then transfer the screenflow to a terminal screen 420 thanking the user 140 for the response.The user 140 may decide to proceed with creating the card and select“next” on screen 400. The screen flow may proceed to screen 410, whichallows the user 140 to preview the birthday card. The birthday card maycontain the sender name (e.g., the name of the user 140), therecipient's name, and a birthday message (e.g., “Wishing you a HappyBirthday Month!”). In some embodiments, the electronic birthday card maycontain a graphic as displayed by the speaking cloud with the message“Happy Birthday” written within.

Upon previewing the card, the user 140 may decide not to proceed withsending the card. In such case, the user 140 may select cancel and thescreen flow may proceed to the terminal screen 420 that thanks the user140 for the response. At screen 410, the user 140 may decide to proceedwith sending the card as previewed by selecting “send card” as shown inFIG. 4. The screen flow may proceed to a confirmation screen 430 thatthanks the user 140 for the personalized happy birthday card request.The confirmation screen 430 may also invite the user 140 to givefeedback to the financial institution regarding the process ofgenerating the card.

FIG. 5 is a schematic screen flow diagram of a process for a recipientto view the happy birthday message generated in FIG. 4, according to anexample embodiment. At screen 510, the recipient may view a first screenof the card of FIG. 4, which may display the sender's name, therecipient's name, and a message. The recipient may engage a field thatallows the recipient to open the card. Upon engaging the field, therecipient may be transferred to animated screen 520, which may show ananimation of characters and graphics relaying the Happy Birthdaymessage.

FIG. 6 is a flow diagram of a process for redeeming a gift attached to amessage, according to an example embodiment. The recipient may receivethe message sent by the user 140 (610). The message may be receivedthrough the ATM 150 or any other platform configured to allow the user140 to generate the message (e.g., a mobile application). In someembodiments, the ATM messaging logic 185 determines that date is withina notification period set by the user 140 and/or the ATM messaging logic18 (e.g., the month of the date) and then triggers the transfer of themessage.

The process may involve displaying the message to the receiver (620).The message can be displayed to the recipient once the recipientaccesses the bank computing system 105 to carry out banking activitiessuch as cash withdrawal, checking balances, depositing funds, etc. Themessage may be displayed to the recipient via a variety of platformsused the by recipient to facilitate the banking activities describedthroughout, including an ATM, mobile device using the financialinstitution website or mobile application, etc. Once the recipient viewsthe message, the recipient may redeem a gift if one is attached to themessage. If the user 140 designated a restricted gift, then therecipient may redeem the gift according to the form chosen by therecipient. Otherwise, the recipient may enter a selection of a giftaccording to the form in which the recipient wishes to redeem the gift,for example, by a cash deposit into a checking or savings account,payment of a past due credit card bill, transfer of rewards points, etc.The process may receive the selection from the recipient to redeem thegift (630). The selection may be received through a touch screen displayor through any interface mechanism available to the recipient (e.g.,ATM, smartphone, tablet, laptop, etc.). Upon receiving the selection,the bank computing system 105 may carry out the transaction to redeemthe gift for the recipient.

The embodiments of the methods and system have been described withreference to drawings. The drawings illustrate certain details ofspecific embodiments that implement the systems and methods and programsof the present disclosure. However, describing the disclosure withdrawings should not be construed as imposing on the disclosure anylimitations that may be present in the drawings. The embodimentsdescribed above contemplate methods, systems and program products storedon any non-transitory machine-readable storage media for accomplishingits operations. The embodiments may be implemented using an existingcomputer processor, or by a special purpose computer processorincorporated for this or another purpose or by a hardwired system.

As noted above, embodiments can include program products comprisingnon-transitory machine-readable storage media for carrying or havingmachine-executable instructions or data structures stored thereon. Suchmachine-readable media may be any available media that may be accessedby a general purpose or special purpose computer or other machine with aprocessor. By way of example, such machine-readable storage media maycomprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage,magnetic disk storage or other magnetic storage devices, or any othermedium which may be used to carry or store desired program code in theform of machine-executable instructions or data structures and which maybe accessed by a general purpose or special purpose computer or othermachine with a processor. Combinations of the above are also includedwithin the scope of machine-readable media. Machine-executableinstructions comprise, for example, instructions and data which cause ageneral purpose computer, special purpose computer, or special purposeprocessing machines to perform a certain function or group of functions.

Embodiments of the present disclosure have been described in the generalcontext of method steps which may be implemented in one embodiment by aprogram product including machine-executable instructions, such asprogram code, for example in the form of program modules executed bymachines in networked environments. Generally, program modules includeroutines, programs, logics, objects, components, data structures, etc.that perform particular tasks or implement particular abstract datatypes. Machine-executable instructions, associated data structures, andprogram modules represent examples of program code for executing stepsof the methods disclosed herein. The particular sequence of suchexecutable instructions or associated data structures represent examplesof corresponding acts for implementing the functions described in suchsteps.

As previously indicated, embodiments of the present disclosure may bepracticed in a networked environment using logical connections to one ormore remote computers having processors. Those skilled in the art willappreciate that such network computing environments may encompass manytypes of computers, including personal computers, hand-held devices,multi-processor systems, microprocessor-based or programmable consumerelectronics, network PCs, minicomputers, mainframe computers, and so on.Embodiments of the disclosure may also be practiced in distributedcomputing environments where tasks are performed by local and remoteprocessing devices that are linked (either by hardwired links, wirelesslinks, or by a combination of hardwired or wireless links) through acommunications network. In a distributed computing environment, programmodules may be located in both local and remote memory storage devices.

An exemplary system for implementing the overall system or portions ofthe disclosure might include a general purpose computing computers inthe form of computers, including a processing unit, a system memory ordatabase, and a system bus that couples various system componentsincluding the system memory to the processing unit. The database orsystem memory may include read only memory (ROM) and random accessmemory (RAM). The database may also include a magnetic hard disk drivefor reading from and writing to a magnetic hard disk, a magnetic diskdrive for reading from or writing to a removable magnetic disk, and anoptical disk drive for reading from or writing to a removable opticaldisk such as a CD ROM or other optical media. The drives and theirassociated machine-readable media provide nonvolatile storage ofmachine-executable instructions, data structures, program modules andother data for the computer. It should also be noted that the word“terminal” as used herein is intended to encompass computer input andoutput devices. User interfaces, as described herein may include acomputer with monitor, keyboard, a keypad, a mouse, joystick or otherinput devices performing a similar function.

It should be noted that although the diagrams herein may show a specificorder and composition of method steps, it is understood that the orderof these steps may differ from what is depicted. For example, two ormore steps may be performed concurrently or with partial concurrence.Also, some method steps that are performed as discrete steps may becombined, steps being performed as a combined step may be separated intodiscrete steps, the sequence of certain processes may be reversed orotherwise varied, and the nature or number of discrete processes may bealtered or varied. The order or sequence of any element or apparatus maybe varied or substituted according to alternative embodiments.Accordingly, all such modifications are intended to be included withinthe scope of the present disclosure. Such variations will depend on thesoftware and hardware systems chosen and on designer choice. It isunderstood that all such variations are within the scope of thedisclosure. Likewise, software and web implementations of the presentdisclosure could be accomplished with standard programming techniqueswith rule based logic and other logic to accomplish the various databasesearching steps, correlation steps, comparison steps and decision steps.

The foregoing description of embodiments of the disclosure has beenpresented for purposes of illustration and description. It is notintended to be exhaustive or to limit the disclosure to the precise formdisclosed, and modifications and variations are possible in light of theabove teachings or may be acquired from practice of the disclosure. Theembodiments were chosen and described in order to explain the principalsof the disclosure and its practical application to enable one skilled inthe art to utilize the disclosure in various embodiments and withvarious modifications as are suited to the particular use contemplated.Other substitutions, modifications, changes and omissions may be made inthe design, operating conditions and arrangement of the embodimentswithout departing from the scope of the present disclosure.

Throughout the specification, numerous advantages of the exemplaryembodiments have been identified. It will be understood of course thatit is possible to employ the teachings herein without necessarilyachieving the same advantages. Additionally, although many features havebeen described in the context of a particular data processing unit, itwill be appreciated that such features could also be implemented in thecontext of other hardware configurations.

While the exemplary embodiments illustrated in the figures and describedabove are presently preferred, it should be understood that theseembodiments are offered by way of example only. Other embodiments mayinclude, for example, structures with different data mapping ordifferent data. The disclosure is not limited to a particularembodiment, but extends to various modifications, combinations, andpermutations that nevertheless fall within the scope and spirit of theappended claims.

What is claimed is:
 1. A method, comprising: receiving identificationinformation of a first account holder at a financial institution;authenticating the first account holder via an automated teller machine(ATM) based on the identification information; identifying a birthday ofthe first account holder, including determining date information for thebirthday; configuring a happy birthday message to be displayed to thefirst account holder based on the birthday; storing triggerconfiguration information comprising a time window including the dateinformation for the birthday; and displaying the happy birthday messageto the first account holder via the ATM, the message being displayedwhen the first account holder accesses the ATM at a time occurringwithin the time window.
 2. The method of claim 1, further comprisingdelivering a gift to the first account holder in association with thehappy birthday message.
 3. The method of claim 2, further comprisingreceiving a user input from the first account holder via the ATM,wherein the user input causes the gift to be delivered to the firstaccount holder.
 4. The method of claim 2, wherein the gift comprisescash dispensed at the ATM when the happy birthday message is displayedto the first account holder.
 5. The method of claim 2, wherein the giftis generated using merchant rewards points accumulated by the firstaccount holder.
 6. The method of claim 1, further comprising:identifying a second account holder at the financial institution asbeing known to the first account holder; and receiving inputs from thesecond account holder to configure the happy birthday message.
 7. Themethod of claim 6, further comprising receiving at least a portion ofthe trigger configuration information from the second account holder. 8.A system for customer transaction machine messaging service comprising:a banking computer system; and a plurality of automated teller machines(ATMs) associated with a financial institution and coupled to thebanking computer system, wherein the ATMs and the banking computersystem in combination are configured to: receive identificationinformation of a first account holder at a financial institution;authenticate the first account holder via an ATM of the plurality ofATMs based on the identification information; identify a birthday of thefirst account holder, including determining date information for thebirthday; configure a happy birthday message to be displayed to thefirst account holder based on the birthday; store trigger configurationinformation comprising a time window including the date information forthe birthday; and display the happy birthday message to the firstaccount holder via the ATM, the message being displayed when the firstaccount holder accesses the ATM at a time occurring within the timewindow.
 9. The system of claim 8, wherein the ATMs and the bankingcomputer system in combination are configured to deliver a gift to thefirst account holder in association with the happy birthday message. 10.The system of claim 9, wherein the ATMs and the banking computer systemin combination are configured to receive a user input from the firstaccount holder via the ATM, wherein the user input causes the gift to bedelivered to the first account holder.
 11. The system of claim 9,wherein the gift comprises cash dispensed at the ATM when the happybirthday message is displayed to the first account holder.
 12. Thesystem of claim 9, wherein the gift is generated using merchant rewardspoints accumulated by the first account holder.
 13. The system of claim8, wherein the ATMs and the banking computer system in combination areconfigured to: identify a second account holder at the financialinstitution as being known to the first account holder; and receiveinputs from the second account holder to configure the happy birthdaymessage.
 14. The system of claim 13, wherein the ATMs and the bankingcomputer system in combination are configured to receive at least aportion of the trigger configuration information from the second accountholder.
 15. A non-transitory computer-readable storage medium havinginstructions encoded thereon that, when executed by one or moreprocessors, cause the one or more processors to perform a methodcomprising: receiving identification information of a first accountholder at a financial institution; authenticating the first accountholder via an automated teller machine (ATM) based on the identificationinformation; identifying a birthday of the first account holder,including determining date information for the birthday; configuring ahappy birthday message to be displayed to the first account holder basedon the birthday; storing trigger configuration information comprising atime window including the date information for the birthday; anddisplaying the happy birthday message to the first account holder viathe ATM, the message being displayed when the first account holderaccesses the ATM at a time occurring within the time window.
 16. Thenon-transitory computer-readable storage medium of claim 15, wherein themethod further comprises delivering a gift to the first account holderin association with the happy birthday message.
 17. The non-transitorycomputer-readable storage medium of claim 16, wherein the method furthercomprises receiving a user input from the first account holder via theATM, wherein the user input causes the gift to be delivered to the firstaccount holder.
 18. The non-transitory computer-readable storage mediumof claim 16, wherein the gift comprises cash dispensed at the ATM whenthe happy birthday message is displayed to the first account holder. 19.The non-transitory computer-readable storage medium of claim 16, whereinthe gift is generated using merchant rewards points accumulated by thefirst account holder.
 20. The non-transitory computer-readable storagemedium of claim 15, wherein the method further comprises: identifying asecond account holder at the financial institution as being known to thefirst account holder; and receiving inputs from the second accountholder to configure the happy birthday message.